Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2020

reference
49-tree-1
name
2020
tree-preservation-order

undefined

49-tpo-1
uprn
address-text
point
POINT (-1.031406 50.886107)
geometry
MULTIPOLYGON (((-1.031349 50.886101,-1.031352 50.886112,-1.031360 50.886122,-1.031372 50.886130,-1.031388 50.886135,-1.031406 50.886137,-1.031423 50.886135,-1.031439 50.886131,-1.031452 50.886123,-1.031460 50.886113,-1.031463 50.886102,-1.031461 50.886090,-1.031453 50.886080,-1.031440 50.886072,-1.031425 50.886067,-1.031407 50.886065,-1.031389 50.886067,-1.031373 50.886072,-1.031361 50.886080,-1.031352 50.886090,-1.031349 50.886101)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL